Method and apparatus for documenting network paths

ABSTRACT

Methods and apparatus for documenting network path connectivity are described that allow a network management system/revision management system (NMS/RMS) to determine what equipment and ports support a network path by interrupting and restoring Power-over-Ethernet (PoE) service on the network path. Upon detecting a loss of PoE service, communication active jacks that support network path connectivity may activate an internal switch that interrupts downstream connectivity. Each communication active jack along the network path may then begin broadcasting a unique message in the upstream direction that is addressed to the NMS/RMS. Upon receiving a unique active jack message, the NMS/RMS may record the information contained within and instruct the communication active jack to reestablish connectivity to the next downstream device. In this manner, as each device along a network path regains connectivity the network path information stored within the NMS/RMS is updated until a complete view of the network path is documented.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No.11/419,243 filed May 19, 2006, which claims priority to U.S. ProvisionalApplication 60/682,395 filed May 19, 2005, which is hereby incorporatedby reference in its entirety. This application incorporates by referencein their entirety U.S. patent application Ser. No. 10/439,716, entitled“Systems and Methods for Managing a Network” filed May 16, 2003 and U.S.application Ser. No. 10/997,600 filed Nov. 23, 2004, entitled“Communication Patch Panels Systems and Methods,” as well as allmaterials incorporated therein by reference.

BACKGROUND

1. Technical Field

This invention pertains to a documentation system for a communicationnetwork.

2. Description of Related Art

One of the difficult challenges faced by IT network managers is thecollection and maintenance of accurate communication networkdocumentation.

SUMMARY

Methods and apparatus are described by which, in various embodiments,communication network devices that support a network connection within acommunication network report to a network management system (NMS), or arevision management system (RMS), in response to an interruption andrestoration of Power-over-Ethernet (PoE) service. The approach allows anNMS and/or an RMS (NMS/RMS) to document a network path. In oneembodiment, a network path is an inter-connected chain of communicationnetwork devices that support a network connection. The network path may,in one embodiment, be documented by interrupting and restoring PoEservice to the network connection.

In this example, upon detecting a loss of PoE service, one or morenetwork path devices may activate an internal switch that disconnectsdownstream connectivity. Downstream connectivity is connectivity in adirection towards end-user equipment supported by the network path,while upstream connectivity is connectivity in a direction away fromend-user equipment supported by the network path. The respective networkpath devices may then initiate the repeated broadcast of a networkmessage in the network path upstream direction that is addressed to theNMS/RMS. However, given that downstream connectivity has beendisconnected, as described above, the NMS/RMS may receive the messagebroadcast by the network path device that is furthest upstream on thenetwork path. That is, the NMS/RMS may receive the message broadcast bythe network path device that is physically closest to the NMS/RMS withrespect to the other network devices that form the network path.

Upon receipt of a network path device broadcast message, the NMS/RMS maystore information received within the broadcast message and may transmita return message to the broadcasting device. The return message mayinstruct the broadcasting device to stop broadcasting and to reconnectdownstream connectivity. In this manner, upstream connectivity isrestored to the next device in the network path. As each subsequentdownstream network path device regains upstream connectivity and reportsto the NMS/RMS, as described above, the NMS/RMS may document the networkpath by storing information that may include the information receivedfrom each reporting network path device as well as the relative order inwhich each of the respective network path device broadcast messages arereceived.

BRIEF DESCRIPTION OF THE DRAWINGS

Exemplary embodiments according to the present invention are describedbelow with reference to the above drawings, in which like referencenumerals designate like components.

FIG. 1 is a schematic diagram of a representative network path within acommunication network;

FIG. 2 is a detail view of features shown in FIG. 1;

FIG. 3 is a block diagram of a first exemplary embodiment of acommunication active jack; and

FIG. 4 is a block diagram of a second exemplary embodiment of acommunication active jack.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

FIG. 1 is a schematic diagram of a representative network path 100within a communication network. As shown in FIG. 1, a switch 102 isconnected to other network components via a network connection (notshown) and via a patch cord 104 to a first patch panel 106. The firstpatch panel 106 is connected to a second patch panel 107 by a patch cord114. The second patch panel 107 is connected to a wall plate 126 thatincludes a communication active jack 124 via horizontal cabling 122. Anend-user device 134 may connect to network path 100 via cable 132 withcable terminator 130.

FIG. 2 is a detail view of patch panel features shown in FIG. 1. Asshown in FIG. 2, each patch panel may include at least one patch panelactive jack 108. Each patch panel active jack 108 may be associated withone or more light emitting diodes (LEDs) or other light emitters thatmay be activated and/or deactivated in support of network cablemove/add/change operations, as described in greater detail below.

A patch panel active jack 108 may connect to a backend cable via ahard-wired (e.g., a punch-down block) or other connection accessible viaa back face of the patch panel. Patch panel active jack 108 may providea standard patch cord interface (e.g., that supports RJ-45 terminatedcables) via a front face of a patch panel. Further, one or more LEDs 110associated with patch panel active jack 108 may be controlled via thepatch panel by the NMS/RMS or other system to direct move/add/changeoperations. Each patch panel active jack 108 may be configured as anindividual modular unit. One or more modular patch panel active jacks108 may be installed within a patch panel chassis. For example, in oneexemplary embodiment, patch panel active jacks 108 installed within apatch panel may connect to and interface with a main patch panel circuitboard, or motherboard.

FIG. 3 is an exemplary block level diagram of a patch panel active jack302 that is connected to and in communication with a patch panelmotherboard 304, as described above. As shown in FIG. 3, a patch panelactive jack 302 may include an upstream network path cable connection306, a downstream network path cable connection 308, a PoE detectionunit 310, a switch controller 312, a switch 314, and a broadcastcontroller 316.

Patch panel active jack 302 may further include a PoE controller 318that manages power received via PoE or from a host device (e.g., patchpanel power supply 340) to operate circuitry within patch panel activejack 302. Further, patch panel active jack 302 may be configured tosupply PoE power to the network path. For example, as shown in FIG. 3,PoE controller 318 may receive power to operate patch panel active jack302 from patch panel power supply 340 or optionally (as indicated inFIG. 3 with dashed lines) via PoE from leads 4 and 5 (pair-3) and leads7 and 8 (pair-4) of upstream network path cable connection 306. Further,PoE controller 318 may supply PoE power to leads 4 and 5 (pair-3) andleads 7 and 8 (pair-4) of downstream network path cable connection 308to provide power to downstream PoE dependent network devices (e.g.communication active jack 124 in wall plate 126 as shown in FIG. 1). Inaddition, patch panel active jack 302 may contain a differentialamplifier, such as an op-amp 320, connected between PoE detection unit310 and each pair of leads connected to PoE detection unit 310.

In reference to FIG. 1, upstream network path cable connection 306corresponds with the hard-wired (e.g., a punch-down block) or otherconnection accessible via a back face of patch panel 106. Downstreamnetwork path cable connection 308 corresponds with the standard patchcord interface (e.g., that supports RJ-45 terminated cables) accessiblevia a front face of patch panel 106.

In FIG. 3, leads 1 and 2 (pair-1) of upstream network path cableconnection 306 may be pass-through lines that deliver PoE power from anupstream PoE source device to each downstream device in the networkpath. As described above, the NMS/RMS may determine what devices andports support a network path by merely interrupting and restoring PoE onthe network path. In response, each downstream device may respond, asdescribed below, to report device information for each device downstreamof the network path device instructed by the NMS/RMS to interrupt andthen restore PoE power on leads 1 and 2.

Referring again now to FIG. 3, PoE detection unit 310 may monitor leads1 and 2 (pair-1) and/or leads 3 and 6 (pair-2) on upstream network pathcable connection 306 for the presence of PoE power provided by anupstream device to patch panel active jack 302. As shown, the signals onpair-1 and/or pair-2 on upstream network path cable connection 306 maybe each differentially amplified before being passed to PoE detectionunit 310 using op-amp 320. Upon failing to detect the presence of PoEpower on pair-1 and/or pair-2 of upstream network path cable connection306, PoE detection unit 310 may notify switch controller 312. Inresponse to the notification, switch controller 312 may activate switch314 to redirect leads 1 and 2 (pair-1) of upstream network path cableconnection 306 to broadcast controller 316 via leads 336 and 338,thereby disconnecting downstream connectivity on pair-1 to the adjacentdownstream device in the network path.

Note that although not shown in FIG. 3, PoE detection unit 310 may beconfigured to monitor any, or all, leads on upstream connection 306 viaconnections similar to the leads shown in FIG. 3 used to monitor pair-1and pair-2. That is, in addition to, or instead of, monitoring pair-1and/or pair-2, pair-3 and/or pair-4 may be monitored. Thus, for example,pair-2 may be monitored while pair-1 of upstream network path cableconnection 306 is switched between downstream network path cableconnection 308 and broadcast controller 316. Further, in addition tomonitoring for the presence of PoE power, PoE detection unit 310 may beconfigured to monitor for other indications that the upstream connection306 is active. For example, PoE detection unit 310 may be configured tomonitor any, or all, wire pairs for the presence of an Ethernet signal,or any other protocol that would indicate that the line is in active userather than, or in addition to, monitoring for the presence of PoEpower. The switch controller 312 and/or the broadcast controller 316 maybe triggered if the PoE power decreases to below a predetermined levelfor a preset amount of time, for example. Thus, if a momentary poweroutage occurs rather than a planned event for system documentation, thesystem may just power back up without going through documentation.Alternatively, the preset amount of time may be short enough such thatany power outage causes the system to document the network upon poweringup the system.

If the upstream network path cable connection 306 is redirected byswitch 314, switch controller 312 may notify broadcast controller 316 ofthe redirection. In response to the notification, broadcast controller316 may begin broadcasting a unique message that includes a uniqueidentifier (e.g., a MAC ID) associated with patch panel active jack 302.The message may be broadcast via lines 336 and 338 onto upstream networkpath cable connection 306 leads 1 and 2, respectively, to the networkconnected NMS/RMS via the next upstream device in the network path.Broadcast controller 316 may continue to broadcast the unique patchpanel active jack message until an acknowledgment message is receivedfrom the NMS/RMS. The message may be received via upstream network pathcable connection 306 or via a network message received from the NMS/RMSvia patch panel motherboard 304. The unique patch panel active jackmessage may be broadcast continuously at a predetermined repetition rateuntil a response is received by patch panel active jack 302. Similarly,the response may be broadcast continuously until a receipt is receivedby the NMS/RMS or until downstream connectivity is restored.

Upon receipt of an acknowledgment message from the NMS/RMS, broadcastcontroller 316 may stop broadcasting, and switch controller 312 mayactivate a switch 314 to reconnect leads 1 and 2 (pair-1) of upstreamnetwork path cable connection 306 to leads 1 and 2 (pair-1) ofdownstream network path cable connection 308, thereby restoringdownstream connectivity on pair-1 to the adjacent downstream device inthe network path. Once connectivity is restored, the unique identifyingmessage broadcast by the broadcast controller of the downstream patchpanel active jack may be transmitted over the restored path to theNMS/RMS.

In this manner, interrupting and restoring PoE on leads 1 and 2 of anetwork path results in each device downstream of the interruptionsuccessively reporting their respective device information to theNMS/RMS where the information may be stored within a dynamicallymaintained network topology information base maintained by the NMS/RMS.

As described above with respect to FIG. 1, each device along a networkpath may include a modular active jack that monitors PoE service and mayrespond, as described above, to maintain a centralized base of networktopology information. This centralized base may be a single electronicdevice or a series of distributed devices. Such a modular active jackmay be installed in a network connected device, such as a patch panel(as described above with respect to FIG. 1 at 106 and 107), a wall plate(as described above with respect to FIG. 1 at 126), or any other devicealong the network path (e.g., a hub, repeater, etc.).

Depending upon the nature of the device within which an active jack maybe installed, the active jack may connect with and interface withelectronics within that device. For example, when installed within anexemplary intelligent patch panel, as described above with respect toFIG. 3, the active jack may connect to leads on a circuit board, ormotherboard, within the host device. As shown in FIG. 3, a host devicesuch as patch panel motherboard 304 may provide an active jack withaccess to an external power supply via power supply 340, access tonetwork connectivity that is independent of the network path supportedby the active jack via network interface 342. Further, the host devicemay include an LED controller 344 that may operate LED(s) 348. LED(s)348 may be used to support network cable move/add/change operationsinvolving connection and disconnection of network cables to/from theactive jack. As shown in FIG. 3, patch panel active jack 302 may receivepower from patch panel power supply 340, and may communicate over anetwork connection supported by patch panel network interface 342.

Further, although not shown in FIG. 3, a second switch may be insertedon pair-2 with leads to broadcast controller 316. The switch on pair-2may be controlled by switch controller 312 in a similar manner as switch314 on pair-1. In such an exemplary embodiment, in response to controlsignals from switch controller 312 to the respective switches, one orboth pair-1 and pair-2 may be re-routed to broadcast controller 316.Broadcast controller 316 may transmit the same or different informationdepending on which pair(s) is being controlled. Broadcast controller 316may be configured to listen for signals transmitted by the NMS on pair-1and pair-2 of upstream network path connection 306. Further, broadcastcontroller 316 may be configured to store the information received fromthe NMS for use in configuring/controlling patch panel active jack 302,and/or may forward the received information to a controller (not shown)on patch panel motherboard 304.

As shown in FIG. 3, patch panel motherboard 304 may support additionalfeatures, such as MAC ID storage 346. MAC ID storage 346 may providepatch panel active jack 302 with a unique MAC ID for broadcast over theupstream network path cable connection 306, in response to a loss of PoEservice, as described above.

FIG. 4 is a block level diagram of an exemplary active jack 402 that isnot supported by additional circuitry and functionality supplied by ahost device, as described above with respect to FIG. 3. For example,communication active jack 124 within wall plate 126 (see FIG. 1) is anexample of such a communication active jack configuration. Otherexamples, may be active jacks attached to passive devices such aspassive (as opposed to intelligent) patch panel cabinets that do notinclude any electronics, or active jacks included within network devicesthat include circuitry, but that do not support functional connectivityto the active jack as described above with respect to FIG. 3. Despite alack of support functions provided by a host device (e.g., anintelligent patch panel), active jack 402 supports the collection ofnetwork path connectivity information in the same manner as patch panelactive jack 302, as described above with respect to FIG. 3.

As shown in FIG. 4, an active jack 402 may include an upstream networkpath cable connection 406, a downstream network path cable connection408, a PoE detection unit 410, a switch controller 412, a switch 414,and a broadcast controller 416. Active jack 402 may further include aPoE controller 418 that manages PoE power received via upstream networkpath cable connection 406 to operate circuitry within active jack 402.Further, active jack 402 may be optionally configured to supply PoEpower to the downstream network path. For example, as shown in FIG. 4,PoE controller 418 may receive power to operate active jack 402 via PoEfrom leads 4 and 5 (pair-3) and leads 7 and 8 (pair-4) of upstreamnetwork path cable connection 406. Further, PoE controller 418 mayoptionally supply (as indicated in FIG. 4 with dashed lines) PoE powerto leads 4 and 5 (pair-3) and leads 7 and 8 (pair-4) of downstreamnetwork path cable connection 408 to provide downstream PoE dependentnetwork devices with power.

In reference to FIG. 1, the upstream network path cable connection 406may correspond with the connection between horizontal cable 122 andactive jack 124 in wall plate 126. The downstream network path cableconnection 408 may correspond with the standard end-user device portinterface that receives a terminator 130 of cable 132 that connects anend-user device 134 to the far downstream end of network path 100.However, depending upon the type of device within which the active jackis embedded, active jack 402 may be present anywhere along the networkpath. For example, an active jack may be embedded within any intelligentdevice capable of supporting the active jack with functionality (e.g.,FIG. 3), or within any intelligent device that may house and that maysupply power to the active jack, but that may provide little else withrespect to functional support to the active jack. Further, an activejack may be embedded within a variety of passive network devices, suchas passive patch panels that provide no power and no functionality.

In the exemplary embodiment depicted in FIG. 4, which is similar to thatof FIG. 3, leads 1 and 2 (pair-1) of upstream network path cableconnection 406 may be pass-through lines that deliver PoE power from anupstream PoE source device to each downstream device on the networkpath. As described above, the NMS/RMS may determine the devices andports that support a network path by interrupting and restoring PoE onthe network path. In response, each downstream device may respond asdescribed below to sequentially report device information for eachdevice downstream of the device instructed by the NMS/RMS to interruptand then restore PoE power on leads 1 and 2.

Referring again now to FIG. 4, PoE detection unit 410 may monitor leads1 and 2 (pair-1) and/or leads 3 and 6 (pair-2) on upstream network pathcable connection 406 for the presence of PoE power provided from anupstream device to active jack 402. Upon failing to detect the presenceof PoE power on pair-1 and/or pair-2 of upstream network path cableconnection 406, PoE detection unit 410 may notify switch controller 412.In response to the notification, switch controller 412 may activateswitch 414 to redirect leads 1 and 2 (pair-1) of upstream network pathcable connection 406 to broadcast controller 416 via leads 436 and 438,thereby disconnecting downstream connectivity on pair-1 to the adjacentdownstream device in the network path.

Next, switch controller 412 may notify broadcast controller 416 of theredirection. In response to the notification, broadcast controller 416may begin broadcasting a unique message that may include a uniqueidentifier (e.g., a MAC ID) associated with active jack 402. The messagemay be broadcast via lines 436 and 438 onto upstream network path cableconnection 406 leads 1 and 2, respectively, to a network connectedNMS/RMS via the next upstream device in the network path. Broadcastcontroller 416 may continue to broadcast the unique patch panel activejack message until an acknowledgment message is received from theNMS/RMS via upstream network path cable connection 406. The uniqueidentifier can be provided from a memory of the broadcast controller416, similar to the broadcast controller 316 above.

Upon receipt of an acknowledgment message from the NMS/RMS, broadcastcontroller 416 may stop broadcasting, and switch controller 412 mayactivate switch 414 to reconnect leads 1 and 2 (pair-1) of upstreamnetwork path cable connection 406 to leads 1 and 2 (pair-1) ofdownstream network path cable connection 408, thereby restoringdownstream connectivity on pair-1 to the adjacent downstream device inthe network path. Once connectivity is restored, the unique identifyingmessage broadcast by the broadcast controller of the adjacent downstreamactive jack may be transmitted over the restored path to the NMS/RMS.

In this manner, interrupting and restoring PoE on leads 1 and 2 of anetwork path may result in each device downstream of the interruptionsequentially reporting its respective device information to the NMS/RMSwhere the information may be stored as an update to a store ofdynamically maintained network path connectivity information maintainedby the NMS/RMS, as described above. The information can be reportedsequentially from the most upstream device (i.e. the device mostproximate electrically to the NMS/RMS or most distal from the end-userdevice) to the most downstream device (i.e. the device most distalelectrically to the NMS/RMS or most proximate from the end-user device).Alternatively, the information can be reported from the most downstreamdevice to the most upstream device or in any other sequence desired, forexample, if the information is reported by the network interface or byleads other than those disconnected from the NMS/RMS.

In an IT infrastructure in which exemplary active jacks (e.g., asdescribed above with respect to FIG. 3 and FIG. 4) are deployed insupport of a network path connectivity, an NMS/RMS may determine networkpath connectivity by interrupting and restoring PoE on the network path.For example, referring now to FIG. 1, if the NMS/RMS were to instructswitch 102 to interrupt and then restore PoE service to the portsupporting network cable 104, each of the respective downstream activejack devices on the network path (e.g., patch panel 106, patch panel107, and wall-plate mounted communication active jack 124) may respondwith unique identifier and/or additional topology information asconnectivity to each of the respective devices is sequentially restored.Further, with respect to FIG. 3, if the NMS/RMS system were tocommunicate via patch panel network interface 342 with an active jackswitch controller 312, the NMS/RMS may instruct active jack switchcontroller 312 to toggle switch 314 in order to temporarily interruptPoE service downstream of the patch panel. In such a scenario, each ofthe respective downstream active jack devices on the network path (i.e.,patch panel 107 and wall-plate mounted communication active jack 124)may respond with unique identifier and/or additional topologyinformation as connectivity to each of the devices is sequentiallyrestored. In this manner, the NMS/RMS may obtain network pathdocumentation updates for any portion of the network to which PoEservice is temporarily interrupted.

Further, the NMS/RMS may automatically receive network path topologyinformation associated each time a physical network cable connection isdisconnected and then reconnected. In such a scenario, the NMS/RMS mayuse the unique identifiers and/or other information included within eachof the respective active jack broadcast messages to update existingnetwork path connectivity information.

The active jack network path reporting capabilities, described above,may be used to support routine network cable move/add/change operations.For example, to facilitate removal of a patch cord between two patchpanels that include active jacks, the NMS/RMS may instruct the two patchpanels to illuminate LEDs associated with the patch panel active jackson each of the respective patch panels that are connected by a commonpatch cord. Further, the NMS/RMS may instruct the active jack associatedwith the downstream patch panel to broadcast the active jack's uniquemessage on the upstream network path connection until PoE service islost. The NMS/RMS may use the pair of leads of the active jack or thenetwork interface of the motherboard to instruct the active jack tobroadcast the active jack's unique message. In addition, the NMS/RMS mayinstruct the downstream patch panel to turn off the LED associated withthe downstream active jack upon the downstream patch panel receivingfeedback from the downstream patch panel active jack that PoE servicehas been lost. In such a scenario, the operator may direct the NMS/RMSto turn off the LED on the upstream patch panel once both ends of thepatch cord are removed. Alternatively, the NMS may automatically turnoff the LED on the upstream patch panel after expiration of anappropriate time frame (e.g., 15 seconds or less to 2 minutes or more).

By way of a second example, to facilitate addition of a patch cordbetween two patch panels that include active jacks, the NMS/RMS mayinstruct the two patch panels to illuminate LEDs associated with thepatch panel active jacks on the respective patch panels to be connectedby a common patch cord. When PoE is detected by the downstream patchpanel active jack, the active jack may respond by transmitting theactive jack's unique message on the upstream network path. If theNMS/RMS determines that the unique message is received via the correctupstream port, the NMS/RMS may turn off both LEDs and the switches onthe respective patch panel active jacks may be actuated to establishdownstream connectivity.

The above discussion relates to only a few of the many ways ofdocumenting network path connectivity within a communication network.The present invention is not limited to analysis of the exemplary ITinfrastructure network paths described above, but may be applied to anyIT network architecture/configuration in which active jacks aredeployed, as described above, to support network path connectivity.

Active jacks may be implemented in any number of modules and are notlimited to any specific hardware or software module architecture. Eachactive jack module may be implemented in any number of ways and is notlimited in implementation to execute process flows precisely asdescribed above. The network path documentation process, describedabove, may be modified in any manner that supports documentation ofnetwork path connectivity.

It is to be understood that various functions of the NMS/RMSfunctionality used in support of the network path documentation processmay be distributed in any manner among any quantity (e.g., one or more)of hardware and/or software modules or units, computer or processingsystems or circuitry.

An active jack that supports the network path documentation process maysupport any type of network cabling that supports PoE power distributionalong a network path. An active jack may support any type of cable andcable connector, including but not limited to RJ-45 based connectors.

An active jack switch (e.g., FIG. 3, at 324) that supports the networkpath documentation process may support the redirection of any type ofnetwork cabling, including but not limited to copper cabling. Althoughan exemplary relay module may be configured to redirect cable conductorsassociated with an RJ-45 connector, such an embodiment is exemplary onlyand should not be interpreted as limiting a relay module to redirectingRJ-45 based conductors exclusively.

NMS/RMS processes associated with the network path documentationprocesses may be integrated within a stand-alone system or may executeseparately and be coupled to any number of devices, workstationcomputers, server computers or data storage devices via anycommunication medium (e.g., network, modem, direct connection, etc.).The NMS/RMS processes associated with the network path documentationprocess can be implemented by any quantity of devices and/or anyquantity of personal or other type of computers or processing systems(e.g., IBM-compatible, Apple, Macintosh, laptop, palm pilot,microprocessor, etc.). The computer system may include any commerciallyavailable operating system (e.g., Windows, OS/2, Unix, Linux, DOS,etc.), any commercially available and/or custom software (e.g.,communication software, load-averaged smoothing process software, etc.)and any types of input devices (e.g., keyboard, mouse, probes, I/O port,etc.).

Communication active jack and NMS/RMS software associated with thenetwork path documentation process may be implemented in any desiredcomputer language, and could be developed by one of ordinary skill inthe computer and/or programming arts based on the functional descriptioncontained herein and the described workflows. For example, in oneexemplary embodiment, support for the network path documentation processwithin an NMS/RMS and/or within the communication active jack may bewritten using the C++ programming language, however, the presentinvention is not limited to being implemented in any specificprogramming language. The various modules and data sets may be stored inany quantity or types of file, data or database structures. Moreover,the software associated with the network path documentation process maybe distributed via any suitable medium (e.g., stored on devices such asCD-ROM and diskette, downloaded from the Internet or other network(e.g., via packets and/or carrier signals), downloaded from a bulletinboard (e.g., via carrier signals), or other conventional distributionmechanisms).

The format and structure of internal structures used to hold networkpath connectivity information in support of the network pathdocumentation process may include any and all structures and fields andare not limited to files, arrays, matrices, status and controlbooleans/variables.

The network path documentation process software within the NMS/RMS maybe installed and executed on a computer system in any conventional orother manner (e.g., an install program, copying files, entering anexecute command, etc.). The functions associated with the network pathdocumentation process may be performed on any quantity of computers orother processing systems. Further, the specific functions may beassigned to one or more of the computer systems in any desired fashion.

The network path documentation process may accommodate any quantity andany type of data set files and/or databases or other structurescontaining stored network path connectivity information in any desiredformat (e.g., ASCII, plain text, any word processor or other applicationformat, etc.).

Network path documentation process output may be presented to a user inany manner using numeric and/or visual presentation formats. Networkpath analysis output may be presented as input to a graphical userinterface or an analysis tool in either numeric or visual form and canbe processed by the analysis tool in any manner and/or using any numberof threshold values and/or rule sets.

Further, any references herein of software performing various functionsgenerally refer to computer systems or processors performing thosefunctions under software control. The computer system may alternativelybe implemented by hardware or other processing circuitry. The variousfunctions of the network path documentation process may be distributedin any manner among any quantity (e.g., one or more) of hardware and/orsoftware modules or units, computer or processing systems or circuitry,where the computer or processing systems may be disposed locally orremotely of each other and communicate via any suitable communicationmedium (e.g., LAN, WAN, Intranet, Internet, hardwire, modem connection,wireless, etc.). The software and/or processes described above may bemodified in any manner that accomplishes the functions described herein.

From the foregoing description it will be appreciated that novel networkpath documentation methods and apparatus are disclosed that are capableof accurately documenting a deployed network infrastructure based uponassessment of network path connectivity within the network.

While specific embodiments of apparatus and methods of documentingnetwork path connectivity are disclosed, these embodiments should beviewed as illustrative, not limiting. Various modifications,improvements and substitutes are possible within the scope of thepresent invention. Although specific terms are employed herein, they areused in their ordinary and accustomed manner only, unless expresslydefined differently herein, and not for purposes of limitation.

1. A method of documenting a network system comprising at least one of anetwork management system (NMS) or a revision management system (RMS)and comprising a connector that contains an upstream network path cableconnection having a plurality of pairs of leads and a downstream networkpath cable connection having pairs of leads corresponding to theplurality of pairs of leads of the upstream network path cableconnection, the method comprising: (a) monitoring a signal provided tothe connector; (b) disconnecting a pair of leads of the upstream networkpath cable connection from the corresponding pair of leads of thedownstream network path cable connection after a predetermined change inthe signal has been detected by the connector; (c) connecting atransmitter in the connector to the pair of leads of the upstreamnetwork path cable connection after the predetermined change in thesignal has been detected by the connector; (d) transmitting a broadcastsignal from the upstream network path cable connection; (e) the at leastone of the NMS or the RMS receiving the broadcast signal and providing aresponse thereto; (f) terminating transmission of the broadcast signalafter the response to the broadcast signal has been received by theconnector; (g) disconnecting the transmitter from the pair of leads ofthe upstream network path cable connection after the response has beenreceived by the connector; and (h) reconnecting the pair of leads of theupstream network path cable connection with the pair of leads of thedownstream network path cable connection after the response has beenreceived by the connector.
 2. The method of claim 1, wherein theconnector monitors Power-over-Ethernet (PoE) power supplied to theupstream network path cable connection.
 3. The method of claim 1,wherein the connector monitors an Ethernet signal supplied to the pairof leads of the upstream network path cable connection.
 4. The method ofclaim 1, further comprising supplying PoE power to the connector, theconnector managing the PoE power to operate the circuitry within theconnector.
 5. The method of claim 1, wherein the connector receives theresponse via a network connection other than the upstream network pathcable connection.
 6. The method of claim 1, wherein the connectorreceives the response via the upstream network path cable connection. 7.The method of claim 1, wherein the system comprises a plurality of theconnectors connected such that the downstream network path cableconnection of an upstream connector is connected to the upstream networkpath cable connection of a downstream connector, the method beingrepeated from the connector furthest upstream sequentially to theconnector furthest downstream.
 8. The method of claim 1, wherein morethan one pair of leads of the upstream network path cable connection isconnectable to and disconnectable from: the corresponding pairs of leadsof the downstream network path cable connection and the transmitter.